Discovering new backup clients

ABSTRACT

A system for discovering new backup clients is disclosed. The system comprises an input interface and a processor. The input interface is configured to receive a notice from a backup client. The processor is configured to provide an indication of the notice and select a configuration mode from a set of available configuration modes.

CROSS REFERENCE TO OTHER APPLICATIONS

This application is a continuation of co-pending U.S. patent applicationSer. No. 14/138,534 entitled DISCOVERING NEW BACKUP CLIENTS filed Dec.23, 2013, which is incorporated herein by reference for all purposes.

BACKGROUND OF THE INVENTION

Configuration of backup services for a network system client on astorage network typically involves creating a client configuration on abackup server. This configuration process can be made simpler for abackup administrator by usage of wizards or even automated, but thebackup administrator must first be made aware of the existence of thenew client.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 is a block diagram illustrating an embodiment of a system fordiscovering new backup clients.

FIG. 2 is a flow diagram illustrating an embodiment of a process forsetting up a new client system.

FIG. 3 is a flow diagram illustrating an embodiment of a process fordiscovering new backup clients.

FIG. 4 is a flow diagram illustrating an embodiment of a process forconfiguring a backup client.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess; an apparatus; a system; a composition of matter; a computerprogram product embodied on a computer readable storage medium; and/or aprocessor, such as a processor configured to execute instructions storedon and/or provided by a memory coupled to the processor. In thisspecification, these implementations, or any other form that theinvention may take, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered within thescope of the invention. Unless stated otherwise, a component such as aprocessor or a memory described as being configured to perform a taskmay be implemented as a general component that is temporarily configuredto perform the task at a given time or a specific component that ismanufactured to perform the task. As used herein, the term ‘processor’refers to one or more devices, circuits, and/or processing coresconfigured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

A system for discovering new backup clients is disclosed. The systemcomprises an input interface and a processor. The input interface isconfigured to receive a notice from a backup client. The processor isconfigured to provide an indication of the notice and select aconfiguration mode from a set of available configuration modes.

In some embodiments, in a networked backup storage system, when a newbackup client is added to the network, it has software installed,including any software deemed required by the organization (e.g., backupclient software, antivirus software, monitoring software, etc.). Thebackup software indicates to a backup server that the client has beenadded to the network. In various embodiments, the backup software comesconfigured with a default address for the backup server, a list ofpotential addresses for a backup server, a process for discovering abackup server in the network of attached servers, or any otherappropriate manner of obtaining a candidate backup server. In someembodiments, the backup software prompts the user running theinstallation for an address for the backup server. In variousembodiments, the backup software send a notification when it is firststarted up, upon each reboot, whenever a significant software package isinstalled, or at any other appropriate time. When the backup serverreceives the notification, it matches it with existing list ofconfigured clients and only if information is new, then it adds it tolist of unconfigured clients and the backup administrator is notified ofa new or modified backup client on the network. The backup administratorcan then provide an indication to the backup server of how to configurethe backup client. In various embodiments, the backup client isconfigured automatically, semi-manually (e.g., a software wizard guidesthe backup administrator through a manual installation), manually (e.g.,by all configuration actions are made by the backup administrator), thebackup client is dismissed (e.g., not configured for backup), theexisting backup configuration is not changed, or the backup client isconfigured or not configured in any other appropriate way. In variousembodiments, the backup client is configured for a full backup, for apartial backup, for a custom backup type (e.g., for database software),for a manual backup, incremental backups, or for any other appropriatebackup type.

FIG. 1 is a block diagram illustrating an embodiment of a system fordiscovering new backup clients. In the example shown, FIG. 1 comprisesnetwork 100. In various embodiments, network 100 comprises one or moreof the following: a local area network, a wide area network, a wirednetwork, a wireless network, the Internet, an intranet, a storage areanetwork, or any other appropriate communication network. In the exampleshown, client system 106 comprises a client system (e.g., a computingsystem for operation by a user). In some embodiments, client system 106comprises a system accessed by a user directly (e.g., the user is inproximity with client system 106). In some embodiments, client system106 comprises a system accessed by a user remotely (e.g., the user isnot in proximity with client system 106, and accesses client system 106via network 100 and a separate user system). Client system 106 comprisesa system running enterprise software (e.g., business software forcreating data, storing data, transmitting data, receiving data, etc.).In some embodiments, client system 106 comprises a system for storingdata on a backup system or retrieving stored data from a backup system.In various embodiments, there are 1, 4, 17, 22, 1459, or any otherappropriate number of client systems communicating with network 100.Backup storage system 102 comprises a computer system for backing updata. Backup system 102 backs up data stored on client system 106. Invarious embodiments, backup system 102 performs full backups of the dataon client system 106 (e.g., makes complete copies of the data), performsincremental backups of the data on client system 106 (e.g., makes copiesof data modified since the last backup), performs a combination of fulland incremental backups of the data on client system 106, or performsany other appropriate kind of backup. In some embodiments, data storedon backup system 102 comprises deduplicated backup data (e.g., data isstored in such a way that multiple copies of the same data are onlystored a single time). In some embodiments, deduplicated backup data issegmented (e.g., broken into chunks which can then be compared todetermine duplicate data). In some embodiments, deduplicated backup datais segmented using a hash function (e.g., a hash function is used todetermine where to divide data into segments). In various embodiments,there are 1, 2, 7, 12, 45, 138, or any other appropriate number ofbackup storage systems communicating with network 100. Backup serversystem 104 comprises a server system for controlling backup storagesystem 102 and client system 106.

FIG. 2 is a flow diagram illustrating an embodiment of a process forsetting up a new client system. In some embodiments, the process of FIG.2 comprises a process for setting up a client system as in client system106 of FIG. 1. In the example shown, in 200, new system software isreceived (e.g., by the client system). In some embodiments, the systemsoftware comprises custom system software for the network system (e.g.,system software to be installed on a corporate network has beencustomized by the network administrator in ways specific to thecorporate network). In 202, it is determined whether the system softwarecontains a default backup server address. In some embodiments, a defaultbackup server address comprises part of a system software customization.If it is determined in 202 that the system software contains a defaultbackup server address, control passes to 204. In 204, the backup serveris notified of the new client. In some embodiments, the notificationcomprises information describing the client system (e.g., hardwarespecifications, configuration information, operating system type,installed software, etc.). The process then ends. In some embodiments,in 204, in the event that the backup server cannot be notified at thedefault backup server address, control passes to 206. If it isdetermined in 202 that the system software does not contain a defaultbackup server address, control passes to 206. In 206, a user (e.g., auser installing the new system software) is prompted for a backup serveraddress. In 208, a backup server address is received from the user.Control then passes to 204.

In some embodiments, the backup server is notified upon install ofsystem software on the backup client (e.g., an operating system upgrade,etc.). In some embodiments, the backup server is notified upon reboot ofthe backup client. In some embodiments, the backup server is notifiedupon installation of software on the backup client (e.g., a newapplication, a database, an enterprise software module, etc.).

In various embodiments, the alternate address for notification of abackup server is received from a list, a selection of an entry in alist, using an autodiscovery process, or any other appropriate manner ofdetermining an alternate address for notification.

FIG. 3 is a flow diagram illustrating an embodiment of a process fordiscovering new backup clients. In some embodiments, the process of FIG.3 is executed by a backup server system (e.g., backup server system 104of FIG. 1). In the example shown, in 300, a notice is received from abackup client. In some embodiments, the notice comprises a notice thatthe backup client is being added to the network (e.g., a notice as issent by a client system in 204 of FIG. 2). In 302, it is determined ifthe client is configured. In various embodiments, it is determined ifthe client is configured by checking a configuration database, a list ofconfigured clients, a configuration status, or any other appropriateconfiguration information. If it is determined in 302 that the client isconfigured, the process ends. If it is determined in 302 that the clientis not configured, control passes to 304. In 304, the client is added toa list of unconfigured clients. In 306, a backup administrator isnotified of a new unconfigured client. In some embodiments, anunconfigured client is configured by the backup administrator. In someembodiments, an unconfigured client is configured at an appropriate timeas determined by the backup administrator. The administrator can beprompted for a selection for configuring a new backup client using amanual, semi-manual (e.g., a wizard), automatic process, or no updateprocess. In some embodiments, the list of options for available aconfiguration processes is based at least in part on the configurationinformation provided as part of the notice from the backup client. Forexample, an installation configuration of the client may not becompatible with an automated process (e.g., a complex database installedin the client cannot be configured for backup automatically) so that theautomatic configuration option is not presented or is not allowed ifselected.

In some embodiments, in the event that the client is determined to beconfigured in 302, the client is added to a list of configured clientswhose configuration has or may have changed, and the administrator isnotified that a change in configuration to the client has occurred. Theadministrator can then be prompted for a selection for updating thebackup configuration using a manual, semi-manual (e.g., a wizard),automatic process, or no update process. In some embodiments, the listof options for available update processes is based at least in part onthe configuration information provided as part of the notice from thebackup client. For example, an installation configuration of the clientmay not be compatible with an automated process (e.g., a complexdatabase installed in the client cannot be configured for backupautomatically) so that the automatic configuration option is notpresented or is not allowed if selected.

FIG. 4 is a flow diagram illustrating an embodiment of a process forconfiguring a backup client. In some embodiments, a backup client isconfigured by a backup administrator. In some embodiments, the processof FIG. 4 is executed by a backup server system (e.g., backup serversystem 104 of FIG. 1) interacting with a backup administrator. In theexample shown, in 400, a client configuration notice is provided to abackup administrator. In some embodiments, the client configurationnotice comprises a notice received by the backup server system from aclient system. In some embodiments, the client configuration noticecomprises information describing the client system (e.g., hardwarespecifications, operating system type, installed software orapplications, etc.). In some embodiments, a backup administrator makes aclient configuration decision based at least in part on the informationdescribing the client system. In some embodiments, a backupadministrator is presented with options based on the configurationinformation the client has provided in the notice (e.g., depending onthe complexity, the administrator is presented with a subset of the setof possible configuration processes: manual, semi-manual, wizard,automatic, no configuration process, etc.). In 402, a clientconfiguration decision is received from a backup administrator.

In 404, it is determined if the client configuration comprises automaticconfiguration. In some embodiments, an automatic configurationconfigures the client system using a default set of configurations thatare applicable to a typical client system. In some embodiments, theautomatic configuration configures the client using a set ofconfigurations that depend on the configuration information that isprovided from the client. For example, a configuration is builtautomatically based on the information provided by the client systemfrom a preprogrammed set of configurations or using an intelligentautomatic configurer. If it is determined in 404 that the clientconfiguration decision comprises automatic configuration, control passesto 406. In 406, the automatic configuration is used, and the processends. If it is determined in 404 that the client configuration decisiondoes not comprise automatic configuration, control passes to 408. In408, it is determined whether the client configuration decisioncomprises semi-manual configuration. In some embodiments, semi-manualconfiguration comprises configuration by a backup administratorinteracting with an automated configuration wizard, allowing the backupadministrator choices in the client configuration. In some embodiments,a semi-manual configuration wizard is used when client configurationinvolves custom configuration for backup of software application data.In some embodiments, different semi-manual configuration wizards areavailable for configuration of different software applications. Forexample, the wizard uses information received from the client system topresent options to the administrator that are selected from to configurethe client for backup. In some embodiments, the wizard probes for andretrieves information from the client system to further provideconfiguration options to an administrator. If it is determined in 408that the client configuration decision comprises semi-manualconfiguration, control passes to 410. In 410, a semi-manualconfiguration wizard is determined. In various embodiments, asemi-manual configuration wizard is determined based at least in part ona client configuration notice, on a backup administrator decision, on acommunication with the client system, or on any other appropriateinformation. In some embodiments, more than one semi-manualconfiguration wizard is determined. For example, depending on installedapplications, each installed application has a wizard to aid in backupconfiguration.

In 412, the client is configured using the wizard, and the process ends.If it is determined in 408 that the client configuration decision doesnot comprise semi-manual configuration, control passes to 414. In 414,it is determined whether the client configuration decision comprisesmanual configuration (e.g., the client is configured by a backupadministrator without automated assistance). If it is determined in 414that the client configuration comprises manual configuration, controlpasses to 416. In 416, a manual configuration is received, and theprocess ends. If it is determined in 414 that the client configurationdoes not comprise manual configuration (e.g., the client configurationdecision comprises no configuration), control passes to 418. In 418, theclient is dismissed, and the process ends. For example, theadministrator has selected not to configure the client.

In some embodiments, a client configuration comprises a backup fraction(e.g., a fraction of the client system to back up). In variousembodiments, a backup fraction comprises a full backup (e.g., all clientsystem data is backed up), a partial backup (e.g., a portion of theclient system data is backed up), a special backup (e.g., part of theclient system data is backed up in a special way specific to a softwaredatabase or application e.g., Oracle™, Outlook™ Exchange™, etc.), or anyother appropriate backup fraction. In some embodiments, a clientconfiguration comprises a backup frequency (e.g., how often backups areautomatically taken). In various embodiments, a backup frequencycomprises once an hour, once a day, once a week, or any otherappropriate backup frequency. In some embodiments a client configurationcomprises a manual backup (e.g., client data is backed up, but noconfiguration for future automatic backups). In some embodiments, aclient configuration comprises a backup retention time (e.g., how longbackups are kept). In some embodiments, a backup retention timecomprises a decreasing fraction of backups kept as time passes (e.g.,backups are taken every day but only one backup/week is kept past onemonth old and only one backup/month is kept past one year old). In someembodiments, the backup configuration comprises a migration schedule(e.g., time in online connected backup (e.g., an online hard drivesystem), time in near line connected backup (e.g., in an online tapelibrary), time in off line backup (e.g., stored off site), time fordeletion, etc.).

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

What is claimed is:
 1. A system for discovering a new backup client,comprising: an input interface configured to receive a notice from abackup client over a network; and a processor configured to: determinewhether the backup client is already configured to perform backups basedat least in part on a hardware and software configuration of the backupclient; in the event that the backup client is not already configured;provide an indication of the notice; determine a set of availableconfiguration modes based at least in part on the to hardware andsoftware configuration of the backup client; and configure the backupclient according to a selected configuration mode.
 2. The system ofclaim 1, wherein the notice is received upon installation of systemsoftware on the backup client.
 3. The system of claim 1, wherein thenotice is received upon reboot of the backup client.
 4. The system ofclaim 1, wherein the notice is received upon installation of applicationsoftware on the backup client.
 5. The system of claim 1, wherein thenotice comprises configuration information.
 6. The system of claim 1,wherein the notice comprises software information.
 7. The system ofclaim 1, wherein the configuration mode comprises an automaticconfiguration mode.
 8. The system of claim 1, wherein the configurationmode comprises a manual configuration mode.
 9. The system of claim 1,wherein the configuration mode comprises a semi-manual configurationmode.
 10. The system of claim 1, wherein the configuration modecomprises no backup.
 11. The system of claim 1, wherein theconfiguration mode is selected based at least in part on a received userinput.
 12. The system of claim 11, wherein the received user inputcomprises a selection of a mode from a set of modes.
 13. The system ofclaim 12, wherein the user is provided a display of the set of modes andprompted to select the mode from the set of modes.
 14. The system ofclaim 1, wherein the selected configuration mode is selected based atleast in part on software installed on the backup client.
 15. The systemof claim 1, wherein the selected configuration mode is selected based atleast in part on a configuration of the client.
 16. A method fordiscovering a new backup client, comprising: receiving a notice from abackup client over a network; determining whether the backup client isalready configured to perform backups based at least in part on ahardware and software configuration of the backup client; in the eventthat the backup client is not already configured, providing anindication of the notice; determining a set of available configurationmodes based at least in part on the hardware and software configurationof the backup client; and configuring the backup client according to aselected configuration mode.
 17. A computer program product fordiscovering a new backup client, the computer program product beingembodied in a non-transitory computer readable storage medium andcomprising computer instructions for: receiving a notice from a backupclient over a network; determining whether the backup client is alreadyconfigured to perform backups based at least in part on a hardware andsoftware configuration of the backup client; in the event that thebackup client is not already configured, providing an indication of thenotice; determining a set of available configuration modes based atleast in part on the hardware and software configuration of the backupclient; and configuring the backup client according to a selectedconfiguration mode.